Azure Maps Traffic Service (preview:1.0)

2025/08/14 • 5 deleted methods

Traffic_GetTrafficFlowTile (removed)
Description __Traffic Flow Tile__ **Applies to**: S0 and S1 pricing tiers. The Azure Flow Tile API serves 256 x 256 pixel tiles showing traffic flow. All tiles use the same grid system. Because the traffic tiles use transparent images, they can be layered on top of map tiles to create a compound display. The Flow tiles use colors to indicate either the speed of traffic on different road segments, or the difference between that speed and the free-flow speed on the road segment in question.
Reference Link ¶

⚼ Request

GET:  /traffic/flow/tile/{format}
{
x-ms-client-id: string ,
subscription-key: string ,
api-version: string ,
format: string ,
style: string ,
zoom: integer ,
x: integer ,
y: integer ,
thickness: integer ,
}

⚐ Response (200)

{
$schema: string ,
}

⚐ Response (400)

{
error:
{
code: string ,
message: string ,
details:
[
string ,
]
,
target: string ,
}
,
}

⚐ Response (401)

{
$headers:
{
www-authenticate: string ,
}
,
$schema:
{
error:
{
code: string ,
message: string ,
details:
[
string ,
]
,
target: string ,
}
,
}
,
}

⚐ Response (403)

{
error:
{
code: string ,
message: string ,
details:
[
string ,
]
,
target: string ,
}
,
}

⚐ Response (404)

{
error:
{
code: string ,
message: string ,
details:
[
string ,
]
,
target: string ,
}
,
}

⚐ Response (500)

{
error:
{
code: string ,
message: string ,
details:
[
string ,
]
,
target: string ,
}
,
}
Traffic_GetTrafficFlowSegment (removed)
Description __Traffic Flow Segment__ **Applies to**: S0 and S1 pricing tiers. This service provides information about the speeds and travel times of the road fragment closest to the given coordinates. It is designed to work alongside the Flow layer of the Render Service to support clickable flow data visualizations. With this API, the client side can connect any place in the map with flow data on the closest road and present it to the user.
Reference Link ¶

⚼ Request

GET:  /traffic/flow/segment/{format}
{
x-ms-client-id: string ,
subscription-key: string ,
api-version: string ,
format: string ,
style: string ,
zoom: integer ,
query: string ,
unit: string ,
thickness: integer ,
openLr: boolean ,
}

⚐ Response (200)

{
flowSegmentData:
{
frc: string ,
currentSpeed: integer ,
freeFlowSpeed: integer ,
currentTravelTime: integer ,
freeFlowTravelTime: integer ,
confidence: number ,
coordinates:
{
coordinate:
[
{
latitude: number ,
longitude: number ,
}
,
]
,
}
,
@version: string ,
openlr: number ,
}
,
}

⚐ Response (400)

{
error:
{
code: string ,
message: string ,
details:
[
string ,
]
,
target: string ,
}
,
}

⚐ Response (401)

{
$headers:
{
www-authenticate: string ,
}
,
$schema:
{
error:
{
code: string ,
message: string ,
details:
[
string ,
]
,
target: string ,
}
,
}
,
}

⚐ Response (403)

{
error:
{
code: string ,
message: string ,
details:
[
string ,
]
,
target: string ,
}
,
}

⚐ Response (404)

{
error:
{
code: string ,
message: string ,
details:
[
string ,
]
,
target: string ,
}
,
}

⚐ Response (500)

{
error:
{
code: string ,
message: string ,
details:
[
string ,
]
,
target: string ,
}
,
}
Traffic_GetTrafficIncidentTile (removed)
Description __Traffic Incident Tile__ **Applies to**: S0 and S1 pricing tiers. This service serves 256 x 256 pixel tiles showing traffic incidents. All tiles use the same grid system. Because the traffic tiles use transparent images, they can be layered on top of map tiles to create a compound display. Traffic tiles render graphics to indicate traffic on the roads in the specified area.
Reference Link ¶

⚼ Request

GET:  /traffic/incident/tile/{format}
{
x-ms-client-id: string ,
subscription-key: string ,
api-version: string ,
format: string ,
style: string ,
zoom: integer ,
x: integer ,
y: integer ,
t: string ,
}

⚐ Response (200)

{
image: string ,
}

⚐ Response (400)

{
error:
{
code: string ,
message: string ,
details:
[
string ,
]
,
target: string ,
}
,
}

⚐ Response (401)

{
$headers:
{
www-authenticate: string ,
}
,
$schema:
{
error:
{
code: string ,
message: string ,
details:
[
string ,
]
,
target: string ,
}
,
}
,
}

⚐ Response (403)

{
error:
{
code: string ,
message: string ,
details:
[
string ,
]
,
target: string ,
}
,
}

⚐ Response (404)

{
error:
{
code: string ,
message: string ,
details:
[
string ,
]
,
target: string ,
}
,
}

⚐ Response (500)

{
error:
{
code: string ,
message: string ,
details:
[
string ,
]
,
target: string ,
}
,
}
Traffic_GetTrafficIncidentDetail (removed)
Description __Traffic Incident Detail__ **Applies to**: S0 and S1 pricing tiers. This API provides information on traffic incidents inside a given bounding box, based on the current Traffic Model ID. The Traffic Model ID is available to grant synchronization of data between calls and API's. The Traffic Model ID is a key value for determining the currency of traffic incidents. It is updated every minute, and is valid for two minutes before it times out. It is used in rendering [incident tiles](https://docs.microsoft.com/en-us/rest/api/maps/traffic/gettrafficincidenttile). It can be obtained from the [Viewport API](https://docs.microsoft.com/en-us/rest/api/maps/traffic/gettrafficincidentviewport).
Reference Link ¶

⚼ Request

GET:  /traffic/incident/detail/{format}
{
x-ms-client-id: string ,
subscription-key: string ,
api-version: string ,
format: string ,
style: string ,
boundingbox: string ,
boundingZoom: integer ,
trafficmodelid: string ,
language: string ,
projection: string ,
geometries: string ,
expandCluster: boolean ,
originalPosition: boolean ,
}

⚐ Response (200)

{
tm:
{
@id: string ,
poi:
[
{
id: string ,
p:
{
x: number ,
y: number ,
}
,
ic: integer ,
ty: integer ,
cbl:
{
x: number ,
y: number ,
}
,
ctr:
{
x: number ,
y: number ,
}
,
cs: integer ,
l: integer ,
r: string ,
dl: integer ,
t: string ,
f: string ,
d: string ,
c: string ,
}
,
]
,
}
,
}

⚐ Response (400)

{
error:
{
code: string ,
message: string ,
details:
[
string ,
]
,
target: string ,
}
,
}

⚐ Response (401)

{
$headers:
{
www-authenticate: string ,
}
,
$schema:
{
error:
{
code: string ,
message: string ,
details:
[
string ,
]
,
target: string ,
}
,
}
,
}

⚐ Response (403)

{
error:
{
code: string ,
message: string ,
details:
[
string ,
]
,
target: string ,
}
,
}

⚐ Response (404)

{
error:
{
code: string ,
message: string ,
details:
[
string ,
]
,
target: string ,
}
,
}

⚐ Response (500)

{
error:
{
code: string ,
message: string ,
details:
[
string ,
]
,
target: string ,
}
,
}
Traffic_GetTrafficIncidentViewport (removed)
Description __Traffic Incident Viewport__ **Applies to**: S0 and S1 pricing tiers. This API returns legal and technical information for the viewport described in the request. It should be called by client applications whenever the viewport changes (for instance, through zooming, panning, going to a location, or displaying a route). The request should contain the bounding box and zoom level of the viewport whose information is needed. The return will contain map version information, as well as the current Traffic Model ID and copyright IDs. The Traffic Model ID returned by the Viewport Description is used by other APIs to retrieve last traffic information for further processing.
Reference Link ¶

⚼ Request

GET:  /traffic/incident/viewport/{format}
{
x-ms-client-id: string ,
subscription-key: string ,
api-version: string ,
format: string ,
boundingbox: string ,
boundingzoom: integer ,
overviewbox: string ,
overviewzoom: integer ,
copyright: boolean ,
}

⚐ Response (200)

{
viewpResp:
{
trafficState:
{
@trafficAge: integer ,
@trafficModelId: string ,
}
,
copyrightIds: string ,
@version: string ,
@maps: string ,
}
,
}

⚐ Response (400)

{
error:
{
code: string ,
message: string ,
details:
[
string ,
]
,
target: string ,
}
,
}

⚐ Response (401)

{
$headers:
{
www-authenticate: string ,
}
,
$schema:
{
error:
{
code: string ,
message: string ,
details:
[
string ,
]
,
target: string ,
}
,
}
,
}

⚐ Response (403)

{
error:
{
code: string ,
message: string ,
details:
[
string ,
]
,
target: string ,
}
,
}

⚐ Response (404)

{
error:
{
code: string ,
message: string ,
details:
[
string ,
]
,
target: string ,
}
,
}

⚐ Response (500)

{
error:
{
code: string ,
message: string ,
details:
[
string ,
]
,
target: string ,
}
,
}